Excavator: Upgrades Baseline to the latest version#384
Merged
bulldozer-bot[bot] merged 3 commits intodevelopfrom Oct 20, 2022
Merged
Excavator: Upgrades Baseline to the latest version#384bulldozer-bot[bot] merged 3 commits intodevelopfrom
bulldozer-bot[bot] merged 3 commits intodevelopfrom
Conversation
fdd4f12 to
8dcdd96
Compare
d8e5483 to
5c72b81
Compare
07a91d6 to
a5db6d0
Compare
a5db6d0 to
5629408
Compare
0c753aa to
ab70704
Compare
2d65196 to
e0563ed
Compare
bad41f7 to
fb465e3
Compare
4f32163 to
31010c5
Compare
31010c5 to
fada46d
Compare
fada46d to
1ef6c06
Compare
e4fc105 to
9f1a81b
Compare
476eef0 to
6b74034
Compare
38c1e18 to
ccae27c
Compare
1fa00dd to
bba3bb8
Compare
bba3bb8 to
691a154
Compare
691a154 to
c840228
Compare
schlosna
approved these changes
Oct 20, 2022
Contributor
|
Thanks, @schlosna! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
excavator is a bot for automating changes across repositories.
Changes produced by the roomba/latest-baseline-oss check.
Release Notes
4.109.0
ImmutablesReferenceEqualitycheck that checks for comparison of Immutables values using reference equality.4.110.0
4.111.0
4.112.0
SafeLoggingPropagationerror-prone check propages log-safety annotations from getters and superclasses/superinterfaces to the type level4.113.0
4.114.0
4.115.0
4.116.0
Automated release, no documented user facing changes
4.117.0
SafeLoggingPropagationcheck and automated fixes:1. Method return statements are analyzed to determine safety of unmarked methods
2. Types are annotated based on the safety of their
toStringmethod, which is a reasonable heuristic for value types that may be logged.4.118.0
4.119.0
4.120.0
4.121.0
4.122.0
NarrowCalculation4.123.0
4.124.0
4.125.0
4.126.0
4.127.0
4.128.0
4.129.0
Automated release, no documented user facing changes
4.130.0
StackOverflowErrors do not occur4.131.0
4.132.0
4.133.0
4.134.0
4.135.0
4.136.0
LazilyConfiguredMappingthat was extracted out to gradle-utils.4.137.0
4.138.0
4.139.0
4.140.0
AvoidNewHashMapIntto warn on uses ofnew HashSet(int).4.141.0
4.142.0
4.143.0
4.144.0
4.145.0
4.146.0
Automated release, no documented user facing changes
4.147.0
Automated release, no documented user facing changes
4.148.0
4.149.0
com.palantir.baseline-java-versionsplugin can now setjavaVersions { distributionTarget = '17_PREVIEW' }to opt-in to Java's--enable-previewflag at compile time.4.150.0
BaselineModuleJvmArgsplugin to once again work as intended in multi-project builds4.151.0
--enable-previewis used4.152.0
Related to google/error-prone issues 632
Adds a
DefaultLocalecheck that replaces uses ofString.toLowerCase()andString.toUpperCase()with the overloads that take aLocale, usingLocale.ROOT.4.153.0
4.154.0
4.155.0
Automated release, no documented user facing changes
4.156.0
4.157.0
junit-reportsplugin.4.158.0
checkUnusedDependenciestasks added bybaseline-exact-dependenciescompatible with Gradle's configure-on-demand feature.4.159.0
There is a certain class of very problematic cases whereby if you have
a method such as the following:
<br>myJerseyResource.register(/* this is of type Object */ object);<br>Then if you supply a resource which includes any
javax.ws.rsannotations on it, then those will not be registered if your Jersey
version is 3.x or later (and you'll only find this out at runtime).
The opposite is also true if you try to supply resources annotated
with
jakarta.ws.rsto Jersey 2.x.To address this, this commit attempts to add an errorprone check
which lets implementors add an annotation
@ForbidJavaxto methodswhich have been knowingly migrated to Jakarta EE9 and cannot
accept legacy javax types.
4.160.0
4.161.0
4.162.0
+ support setting preview on a project-by-project basis.
+ Fixes #2340
+ fails more elegantly if javaVersions is set on not-the-root.
4.163.0
4.164.0
CyclomaticComplexitycheck is now configured withswitchBlockAsSingleDecisionPoint.4.165.0
com.palantir.baseline-null-awaywhich registers theNullAwaycheck atWARNING. Projects which fail on warnings will require this to pass pre-merge.4.166.0
Automated release, no documented user facing changes
4.167.0
Automated release, no documented user facing changes
4.168.0
4.169.0
4.170.0
4.171.0
com.palantir.baseline-null-awayno longer enables theCheckOptionalEmptinesschecker by default.4.172.0
Automated release, no documented user facing changes
4.173.0
4.174.0
4.175.0
4.176.0
4.177.0
4.178.0
4.179.0
build()with the more descriptivebuildOrThrow(), howeverbuildKeepingLast()may be the original intent in some cases.4.180.0
4.181.0
4.182.0
To enable or disable this check, please contact the maintainers of Excavator.